Velux integration: add the KLF 200 gateway as device #155434
Open
+65
−25
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hey there @Julius2342, @DeerMaximum, @pawlizio, mind taking a look at this pull request as it has been labeled with an integration ( Code owner commandsCode owners of
|
There was a problem hiding this comment.
Pull Request Overview
This PR refactors the Velux integration to introduce a gateway device and improve the data structure by wrapping runtime data in a dataclass. The changes enable proper device hierarchy where Velux devices (windows, lights, covers) are connected via the KLF 200 Gateway.
Key changes:
- Introduced
VeluxDatadataclass to store both the PyVLX instance and gateway device identifier - Created a gateway device entry in the device registry during setup
- Updated all entities to link to the gateway via
via_device - Renamed
configparameter toconfig_entryacross platform setup functions for consistency
Reviewed Changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
homeassistant/components/velux/__init__.py |
Adds VeluxData dataclass, creates gateway device in device registry, updates type hint for VeluxConfigEntry |
homeassistant/components/velux/entity.py |
Updates VeluxEntity.__init__ to accept VeluxConfigEntry instead of string ID, adds via_device to device info |
homeassistant/components/velux/binary_sensor.py |
Updates platform setup to use new data structure and passes config_entry to entity constructors |
homeassistant/components/velux/cover.py |
Updates platform setup to use new data structure and passes config_entry to entity constructors |
homeassistant/components/velux/light.py |
Updates platform setup to use new data structure and passes config_entry to entity constructors |
homeassistant/components/velux/scene.py |
Updates platform setup to use new data structure (scenes don't use VeluxEntity) |
tests/components/velux/test_binary_sensor.py |
Adds test verification for gateway device association via via_device_id |
This was referenced Oct 31, 2025
wollew
force-pushed
the
add_gateway_device
branch
from
6d0b87f to
2a999bd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed change
This PR adds the KLF 200 gateway as its own device and makes it the via_device for all other devices. Currently there are no entities associated with the gateway device, but the PR prepares to add a button in a next step which can reboot the gateway and eventually replace the
reboot_gatewayservice. So the plan is to follow up this PR with two more once it is merged, one to add the reboot-button and the second to deprecate the service.Follow-up PRs:
Type of change
Additional information
Checklist
ruff format homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all.To help with the load of incoming pull requests: